Remote monitoring devices and related methods and systems with audible aed signal listening

ABSTRACT

A remote monitoring device and related systems and methods for monitoring and managing by a monitoring service via a communications network a condition of an AED based on audio signals from the AED. The remote monitoring device includes a housing configured to be positioned outside of the AED such that audio sounds from the AED can be detected. The housing contains at least one processor, a communications module, a first audio sensor, a first audio detection circuitry, a second audio sensor, and a second audio detection circuitry. The communications module is operably connected to the at least one processor and configured to transmit electronic communications to the monitoring service via the communications network. The at least one processor is configured to power on in response to the wakeup notification signal, process digital audio signals, and transmit a signal to the monitoring service to report a condition of the AED.

TECHNICAL FIELD

This disclosure relates to remote monitoring and management of one ormore Automated External Defibrillator(s) (AED), for example, by remotemonitoring devices located in the proximity of an existing AED thatlisten to audio signals from the AED and relay condition information viaa communications network and related methods and systems.

BACKGROUND

Remotely deployed AEDs, especially those located in homes, offices, andpublic spaces, require monitoring to ensure peak performance andreadiness for use. These types of devices, however, usually lackcontinual and frequent monitoring for proper maintenance by trainedtechnical specialists. This is especially true of publicly accessibleAEDs which are not located in hospitals or health care institutions.Publicly accessible AEDs are required to be dependable devices ready forrapid use by untrained members of the general public such that the AEDsare ready to use without servicing or maintenance during an emergency.

Some past approaches to addressing AED monitoring involve augmentingAEDs themselves with an embedded means of bi-directional, wirelesscommunication for sending and receiving useful monitoring data. However,AEDs with embedded bi-directional wireless communications can requireowners and manufacturers to expend a substantial amount of specializedand financial resources to monitor, augment and defend against threats.Moreover, the large number of AEDs already in service would needreplacement for this type of monitoring. Such efforts can be costly intheir development and execution and can delay other AED improvements.

Other approaches to AED monitoring have been suggested that involve AEDmonitoring stations or devices. However, many of these have limitationsor undesirable configurations for listening structures, device testing,provisioning, or overall system design and integration which could useimprovements. AED devices may be installed in wide variety of locationswith a wide range of supporting infrastructure as well as ambientconditions. Monitoring devices that require installation and/orconnection to power and communication systems are thus not well-suitedfor such a wide range of installation environments. Likewise, the widerange of ambient conditions in which AED devices may be installedcomplicates the monitoring environment for both visual and audiomonitoring of such devices and increases the problems for consistent andreliable remote monitoring of such devices.

Accordingly, remote monitoring devices, systems or methods enablingeffective remote collection of AED condition information that can berelayed via a communications network across a wide range of installationand monitoring environments for both new and existing AED devices aredesired.

SUMMARY

Embodiments described or otherwise contemplated herein substantiallyprovide the advantages of improved devices, systems, and methods thatenable enhanced remote monitoring and management of one or more AEDs.Accordingly, proper maintenance and readiness of AEDs is made possibleacross a wide range of installation and monitoring environments for bothnew and existing AED devices.

An embodiment relates to a remote monitoring device for monitoring andmanaging by a monitoring service via a communications network acondition of an AED based on audio signals from the AED The remotemonitoring device includes a housing configured to be positioned outsideof the AED such that audio sounds from the AED can be detected. Thehousing contains at least one processor, a communications module, afirst audio sensor, a first audio detection circuitry, a second audiosensor, and a second audio detection circuitry. The communicationsmodule is operably connected to the at least one processor andconfigured to transmit electronic communications to the monitoringservice via the communications network. The first audio detectioncircuitry is operably connected to the first audio sensor and the atleast one processor. The first audio detection circuitry is configuredto generate a wakeup notification signal when the first audio detectioncircuitry detects audio sounds during a predetermined detectioninterval. The second audio detection circuitry is operably connected tothe second audio sensor and the at least one processor. The second audiodetection circuitry is configured to power on in response to the wakeupnotification signal and commence an active listening mode to providedigital audio signals to the at least one processor. The at least oneprocessor is configured to power on in response to the wakeupnotification signal, process the digital audio signals, and transmit asignal to the monitoring service to report a condition of the AED basedon the digital audio signals that are processed.

An embodiment relates to a remote monitoring device for monitoring audiosignals from an AED and electronically reporting to a monitoring servicevia a communications network. The remote monitoring device includes ahousing configured to be positioned outside of the AED such that audiosounds from the AED can be detected. The housing contains acommunications module, a first audio sensor, a first audio detectioncircuitry, a second audio sensor, a second audio detection circuitry,and at least one processor. The communications module is configured totransmit electronic communications to the monitoring service via thecommunications network. The first audio detection circuitry is operablycoupled with the first audio sensor. The first audio detection circuitryis configured to detect audio sounds from the AED via the first audiosensor. The second audio detection circuitry is operably coupled withthe second audio sensor, the second audio detection circuitry configuredto detect the audio sounds from the AED via the second audio sensor. Theat least one processor is operably coupled with the communicationsmodule, the first audio detection circuitry, and the second audiodetection circuitry. The at least one processor configured to: power onthe first audio detection circuitry during a periodic detection intervalto detect the audio sounds during the periodic detection interval;process signals from the first audio detection circuitry and generate awakeup notification signal in response to the detected audio soundsduring the periodic detection interval; activate the second audiodetection circuitry to commence an active listening mode in response tothe generated wakeup notification signal; process signals from thesecond audio detection circuitry during the active listening mode tomake a determination that the AED is in need of service; and transmit areport signal to the monitoring service based on the determination thatthe AED is in need of service.

An embodiment relates to a remote monitoring device for monitoring audiosignals from an AED and electronically reporting to a monitoring servicevia a communications network. The remote monitoring device includes ahousing configured to be positioned outside of the AED such that audiosignals from the AED can be detected. The housing contains acommunications module, at least one audio sensor, at least one audiodetection circuitry, and at least on processor. The communicationsmodule is configured to transmit electronic communications to themonitoring service via the communications network. The at least oneaudio detection circuitry is operably coupled with the at least oneaudio sensor. The at least one audio detection circuitry is configuredto detect audio sounds from the AED via the at least one audio sensor.The at least one processor is operably coupled with the communicationsmodule and the at least one audio detection circuitry. The at least oneprocessor is configured to: process signals from the at least one audiodetection circuitry based on the detected audio sounds; detect a firstaudio signal from the processed signals; in response to the first audiosignal being detected, commence an active listening mode to detect asecond audio signal from the processed signals and confirm that thesecond audio signal meets a predetermined criterion associated with theactive listening mode; in response to the second audio signal beingdetected, re-commence the active listening mode to detect a third audiosignal from the processed signals and confirm that the third audiosignal meets the predetermined criterion associated with the activelistening mode; and transmit a report signal to the monitoring serviceif the third audio signal meets the predetermined criterion.

An embodiment relates to a remote monitoring device for monitoring audiosignals from an AED and electronically reporting to a monitoring servicevia a communications network. The remote monitoring device includes ahousing configured to be positioned outside of the AED such that audiosignals from the AED can be detected. The housing contains at least oneprocessor, a communications module, a first audio sensor, a first audiodetection circuitry, a second audio sensor, and a second audio detectioncircuitry. The communications module is operably connected to the atleast one processor and is configured to transmit electroniccommunications to the monitoring service via the communications network.The first audio detection circuitry is operably connected to the firstaudio sensor and the at least one processor. The second audio detectioncircuitry is operably connected to the second audio sensor and the atleast one processor. The at least one processor is configured to: residein a low power sleep state by default; commence a detection state forwakeup confirmation during a detection interval in which the first audiodetection circuitry is configured to power on and generate a wakeupnotification signal when the first audio detection circuitry detectsaudio sounds during the detection interval via the first audio sensor;commence a listening state for alert confirmation in response to thewakeup notification signal in which the second audio detection circuitryis configured to power on and provide digital audio signals to the atleast one processor in an active listening mode; and commence atransmission state, upon confirmation of at least three consecutivequalifying tones in the audio signals detected in correspondingqualifying intervals during the digital listening state, in which thecommunications module is caused to transmit a message to the monitoringservice via the communications network indicating a status of the AED.

An embodiment relates to a remote monitoring device for monitoring audiosignals from an AED and electronically reporting to a monitoring servicevia a communications network. The remote monitoring device includes ahousing configured to be positioned outside of the AED but in a closeproximity such that audio signals and personal area network (PAN)wireless signals from the AED can be detected. The housing contains atleast one processor, a communications module, a first audio sensor,audio detection circuitry and PAN wireless circuitry for short-range PANcommunication protocols such as the Internet of Things (IOT) orBluetooth Low Energy (BLTE) or Near Field Communications (NFC). Thecommunications module is operably connected to at least one processorand is configured to transmit electronic communications to themonitoring service via the communications network via one or more of alocal area network (LAN) Internet connection such as WiFi, or a widearea network (WAN) Internet/telephone connection as a cellularconnection, such as 3G, 4G or 5G communication protocols, or a satelliteInternet connection such as Low Earth Orbit (LEO) SIM cards. In variousembodiments, the at least one processor is configured to: reside in alow power sleep state by default; commence a detection state for wakeupconfirmation during a detection interval in which the audio detectioncircuitry is configured to power on and generate a wakeup notificationsignal when the audio detection circuitry detects audio sounds duringthe detection interval. In response to the wakeup notification signal,the at least one processor is configured to receive and analyze at leastone of audible sounds and/or short-range wireless communications fromthe AED, and the communications module is then selectively caused totransmit a message to the monitoring service via the communicationsnetwork indicating a status, a parameter and/or a change in a status ora parameter of the AED or of the communication link between the AED andthe remote monitoring device. In one embodiment, the audio detectioncircuitry includes a first audio detection circuitry, a second audiosensor, and a second audio detection circuitry wherein a wakeupnotification signal is generated when a first audio detection circuitrydetects audio sounds during the detection interval via the first audiosensor; commence a listening state for alert confirmation in response tothe wakeup notification signal in which the second audio detectioncircuitry is configured to power on and provide digital audio signals tothe at least one processor in an active listening mode; and commence atransmission state, upon confirmation of at least three consecutivequalifying tones in the audio signals detected in correspondingqualifying intervals during the digital listening state, in which thecommunications module is caused to transmit a message to the monitoringservice via the communications network. In some embodiments, the digitallistening state can monitor audible signals from the AED, one-wayshort-range PAN wireless signals from the AED, or a combination of both,including in various embodiments configured to monitor both signals forconfirmation and/or verification of one or both of wakeup signals orstatus signals to reduce false positive alerts.

In some embodiments, the communications module includes switchingcircuitry configured to selectively switch among two or more of theInternet connection, cellular connection and/or satellite connection. Invarious embodiments, the switching circuit may be activated by commandsfrom the mobile app or by the remote monitoring device in response todetection of a communication issues between the communications model andthe monitoring service via the communication network.

In some embodiments, a location of the remote monitoring device may bedetermined from cellular location triangulation and/or an optional GPScircuit. In such embodiments, the location determination of the remotemonitoring device enables initial programming and setup of pairs of AEDsand corresponding remote monitoring devices in a central location beforedeployment of the pairs of an AED and a corresponding remote monitoringdevice to different physical locations in a facility or campus.

In some embodiments, the remote monitoring device further includes aphysical indicator, such as a low-power LED indicator, of the status ofthe communication link between the AED and the remote monitoring device,wherein the status of the communication link may be indicated inresponse to a proximity detection between the AED and the remotemonitoring device.

An embodiment relates to a remote monitoring device for monitoring audiosignals from an AED and electronically reporting to a monitoring servicevia a communications network. The remote monitoring device includes ahousing configured to be positioned outside of the AED such that audiosignals from the AED can be detected. The housing contains at least oneprocessor, a memory, a communications module, a speaker, at least oneaudio sensor, and at least one audio detection circuitry. The memory isoperably connected to the at least one processor. The communicationsmodule is operably connected to the at least one processor andconfigured to transmit electronic communications to the monitoringservice via the communications network. The speaker is operablyconnected to the at least one processor and configured to generate audiosounds as part of a self-test of the remote monitoring device. The atleast one audio detection circuitry is operably coupled with the atleast one audio sensor. The at least one audio detection circuitry isconfigured to detect audio sounds via the at least one audio sensor andprovide digital audio signals to the at least one processor. The atleast one processor is configured to: periodically cause the speaker togenerate the audio sounds as part of the self-test of the remotemonitoring device; receive the digital audio signals to confirm that theaudio sounds as part of the self-test of the remote monitoring deviceoriginate from the speaker; and transmit a message conveying results ofthe self-test of the remote monitoring device to the monitoring servicevia the communications network.

An embodiment relates to a system for AED monitoring utilizing a mobiledevice. The system includes a mobile application and a remote managementserver. The mobile application is configured to be executable on themobile device to receive data about an AED and an AED remote monitoringdevice. The remote management server is configured to communicate withthe mobile device and receive data from the mobile device. The mobileapplication executable on the mobile device is configured to: establisha communications connection between the mobile device and the AED remotemonitoring device; establish a communications connection between themobile device and the remote management server; receive a location of atleast one of the AED or the AED remote monitoring device; use thecommunications connection between the mobile device and the AED remotemonitoring device and the location to configure the AED remotemonitoring device with site-specific parameters; and communicate anotification to the remote management server of an attempt of the AEDremote monitoring device to connect to the remote management server.

An embodiment relates to a method for AED monitoring utilizing a mobiledevice. The method includes establishing, by a mobile applicationconfigured to be executable on a mobile device, a communicationconnection between the mobile device and the AED remote monitoringdevice. The method includes establishing, by the mobile application, acommunications connection between the mobile device and a remotemanagement server that is configured to communicate with the mobileapplication and receive data from the mobile device. The method includeslaunching, by the remote management server, an AED kit engine upondetermining that a mobile application is activated on the mobile device.The method includes executing, by the remote management server, the AEDkit engine to establish an AED kit that pairs the AED and the AED remotemonitoring device and includes at least product data about the AED andthe AED monitoring device. The method includes receiving, via at leastone of the mobile application or the remote management server, an AEDkit location. The method includes configuring, via at least one of themobile application or the remote management server, the AED remotemonitoring device with site-specific parameters using the communicationsconnection. The method includes communicating, via at least one of themobile application or the remote management server, a notification of anattempt of the AED remote monitoring device to connect to the remotemanagement server.

An embodiment relates to a system for AED monitoring utilizing a mobiledevice. The system includes a mobile application and a remote managementserver. The mobile application is configured to be executable on themobile device to receive identification data about an AED and an AEDremote monitoring device. The remote management server is configured tocommunicate with the mobile device and receive data from the mobiledevice. The mobile application is executable on the mobile device isconfigured to: establish a communications connection between the mobiledevice and the AED remote monitoring device; establish a communicationsconnection between the mobile device and the remote management server;and program the AED with an updated configuration via at least one ofthe mobile device or the AED remote monitoring device. In embodiments,the updated configuration programming accounts for any prior AED statusinformation communicated to the mobile application during a priorself-test.

The above summary is not intended to describe each illustratedembodiment or every implementation of the subject matter hereof. Thefigures and the detailed description that follow more particularlyexemplify various embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter hereof may be more completely understood in considerationof the following detailed description of various embodiments inconnection with the accompanying figures, in which:

FIG. 1 is a perspective view of a remote monitoring device, according toan embodiment.

FIGS. 2A-2B each is a hardware architecture diagram of a remotemonitoring device, according to an embodiment.

FIGS. 3A-3B each is a diagram of a system for remote monitoring,according to an embodiment.

FIG. 4 is a diagram of an audio circuit and active listening timingdiagram, according to an embodiment.

FIG. 5 is a flow diagram of operations for the remote monitoring device,according to an embodiment.

FIG. 6 is a self-test operation diagram for the remote monitoringdevice, according to an embodiment.

FIG. 7 is a diagram of the communications flow for a Wi-Fi module in asystem for AED remote monitoring, according to an embodiment.

FIG. 8 is a diagram of the communications flow for a IOT network modulein a system for AED remote monitoring, according to an embodiment.

FIG. 9 is an architecture diagram of the mobile application for theremote monitoring device system, according to an embodiment.

FIG. 10 shows a diagram of the data flow for a remote monitoring devicesystem, according to an embodiment.

FIGS. 11A-C are screenshots of the interface of a mobile application forremote monitoring of AEDs shown on a mobile device, according to anembodiment.

FIG. 12 is a diagram of the remote monitoring device software subsystem,according to an embodiment.

While various embodiments are amenable to various modifications andalternative forms, specifics thereof have been shown by way of examplein the drawings and will be described in detail. It should beunderstood, however, that the intention is not to limit the presentdisclosure to the particular embodiments described. On the contrary, theintention is to cover all modifications, equivalents, and alternativesfalling within the spirit and scope of the subject matter as defined bythe claims.

DETAILED DESCRIPTION OF THE DRAWINGS

AEDs provide accessible life-saving tools that must be ready for rapiduse. In order to maintain this readiness, it is beneficial to employ AEDmonitoring devices that are either internal or external to an AED. SuchAED monitoring devices are configured to detect indications that an AEDis in need of maintenance and then send information to a remote locationto provide, for example, an indication of a need for service orattention for the AED.

AED monitoring devices according to the present disclosure areadvantageously designed to address existing limitations. For example,embodiments described herein reduce power consumption by monitoringdevices so that they are not required to expend significant powercontinually or periodically detecting audio or visual indications froman AED, while also being able to detect noise and nearby sounds/data.AED monitoring devices of the present disclosure also limit powerexpenditure that is typically required in identifying tones thatdetermine maintenance conditions requiring attention, and hence, limitthe frequency of battery replacement. As a result, embodiments of thepresent disclosure reduce significant maintenance of these monitoringdevices themselves which would otherwise undermine efforts to minimizemaintenance trips and checking up on devices in person.

Embodiments of the present disclosure address existing problems ofbattery consumption and poor AED audio tone determination, for example,by using a combination of two separate audio detection circuitries (suchas a separate analog microphone and a separate digital microphone, forexample) as a listening structure for detecting AED tones. In disclosedarrangements, a first audio detection circuitry can be of low powerconsumption. The first audio detection circuitry only triggers furtherevaluation by a second higher power consumption circuitry of greatercertainty when certain conditions are met. Accordingly, battery life ofa remote monitoring device is extended, frequent power sourcereplacement is unnecessary, and long-term reliability is achieved byembodiments disclosed herein.

For example, a remote monitoring device with minimal battery consumptionwould be particularly useful in situations where an AED is deployed at alocation that may not be specifically visited or maintained for a yearor multiple years. Under typical conditions for some embodiments, aremote monitoring device could be expected to have its battery orbatteries last for at least four years without requiring replacement.This type of time frame for embodiments of the remote monitoring devicecan be reliably achieved under proposed embodiments despite reliance onoff-the-shelf batteries that are not necessarily well controlled forlongevity of power output. The flexibility and long-term reliabilitythat this provides to users maintaining AEDs can be advantageous.Moreover, having a second audio sensor, such as a digital microphone,that is capable of providing a high level of discriminating analysis,and that is also redundant in certain respects of the first audiosensor, provides an advance to achieving monitoring devices of reliablestructure.

In some embodiments, listening arrangements can provide various statesby the processor of a remote monitoring device which allow for such lowpower consumption and extended lifetime performance. The states of thedevice made possible can include a default low power sleep state, adetection state for wakeup confirmation, a listening state for alertconfirmation, and a transmission state. Efficient monitoring of powerconsumption is achieved by such an arrangement involving device statesand associated functional operations.

Another issue that is addressed by remote monitoring devices describedherein is the problem of false detection of nuisance noises AEDs cansometimes be located in very noisy environments in public places. Forexample, AEDs may be located near gymnasiums, workout rooms, or pools infitness facilities, community centers or schools. Likewise, significantbackground noise is often found at AED locations in malls, front desksof busy buildings, amusement parks and transportation sites, andconstruction environments. Furthermore, the ambient and nuisance noisefrom such environments can vary greatly over the course of a day andfrom day to day. Accordingly, distinguishing nuisance noise from AEDproduced audio signals is extremely important as false positive alertsundermine the ability of an audio monitoring device to function properlyand can waste important AED maintenance resources to follow up on.

Embodiments disclosed provide arrangements in which successive beeps aredetected by a monitoring device with increasing discrimination. Thisapproach prevents nuisance noise from being incorrectly identified as analert beep from the AED. In some embodiments, an advantageous listeningstructure arrangement is disclosed in which at least three audio beepsare used to confirm an AED signal and trigger transmission of an alertto a monitoring system. This type of triple check provides extraconfirmation that detected signals have the appropriate signatures andoccur within the appropriate intervals. This arrangement serves toreduce false positive detection of signals and increases confidence inthe reporting conducted by the monitoring device. Multiple confirmationsof signals received in order proves to be an effective means atfiltering out sounds that are merely nuisance noise and not actuallybeeps or audio signals from the AED indicative of self-test failures ormaintenance requests. An example situation where this triple check couldbe useful from a user perspective could occur if significant noiseresulted in detection of two incorrectly identified chirp sounds in anoisy public environment where audio signals matching a variety ofcriteria could be inadvertently produced. Without the third check, anunacceptable false positive could occur at times. Unnecessarymaintenance and service requests and resource commitments could result.In these embodiments, the third check can largely eliminate this type offalse positive detection, as it would be extremely unlikely that merenuisance noise could match any actual AED alert signal for all threechecks.

Other issues that are overcome by embodiments of the present disclosure,for example, may relate to tracking whether the monitoring devicesthemselves are functioning properly, such as in monitoring for thingslike battery failure or errors. Unreported failures of monitoringdevices can result in AED failures themselves not being reported.Further, unreliable alerts of monitoring device failures only serve torequire additional undesired maintenance. Embodiments disclosed includea self-test capability for remote monitoring devices themselves, suchthat appropriate maintenance of these devices can be carried out whennecessary and the integrity of the reporting system is achieved.

An example situation where this feature might be particularly usefulcould be in instance where an error in the remote monitoring devicecircuitry occurs or a faulty battery is present in the device. Theself-test feature for the remote monitoring device can allow a remotesystem to determine if the remote monitoring device has detected acommunication error with the AED, such as the remote monitoring devicenot being within a general proximity of the AED, or the remotemonitoring device has not checked in with the remote system for adesignated period of time such that a no-check in alert can be made.This enables a user to correct the issue with the remote monitoringdevice quickly and provides confidence in its ongoing integrity overtime.

Other issues that monitoring devices in accordance with the presentdisclosure addresses are the challenges associated with set-up,provision, and appropriately group monitoring devices with the AEDS themonitoring devices are intended to monitor. Embodiments disclosed hereinaddress this issue by providing a mobile app that allows forcommunication between a mobile device and a remote monitoring device toconfigure the remote monitoring device. Accordingly, the mobile app isconfigured to effectively link the remote monitoring device to the AEDthat it is monitoring. Methods of controlling the mobile app and furtherdisclosure related to these embodiments are included as well.

Examples of situations where this can be particularly useful to usersinclude instances where an AED is being deployed with a remotemonitoring device to establish a pairing for the first time the remotemonitoring device or the AED is installed. Utilizing the mobile app toassociate and link a remote monitoring device to an AED andsimultaneously identify a location of this pairing with the GPS of themobile device running the mobile app saves significant time and reducesuser error in set-up. Later updates can efficiently be provided quicklyand easily utilizing this known pairing as well.

Embodiments disclosed relate to devices, systems, and methods thatenable enhanced remote monitoring and management of one or more AEDs 10,so that proper maintenance and readiness can be provided to theselife-saving medical devices.

FIG. 1 shows an example of a remote monitoring device 100 from aperspective view. The remote monitoring device 100 is relatively smallin size and largely enclosed in a housing 102 which generally surroundsthe internal hardware that is located therein. Numerous other sizes andshapes of housings 102 are possible. At times, throughout thespecification and figures, the remote monitoring device 100 mayalternatively be referred to as an “AED Tag”, “AED monitor”, or “AEDmonitoring device” and should be broadly interpreted and understood toencompass this terminology.

The remote monitoring device 100 is intended for physical co-locationwith an AED 10. Specifically, the remote monitoring device 100 isintended for location within the general proximity of an AED 10 suchthat audio sounds 104 made by the AED 10, providing important audiosignals that provide information related to the operational status ofthe AED 10 (e.g., whether the AED and/or parts associated therewith arefully functional), can be detected by the remote monitoring device 100.Accordingly, the remote monitoring device 100 is designed to have thecapability to detect the acoustical tones that an AED 10 emits when itrequires service or otherwise is providing an update as to itsfunctional status.

In some embodiments, the AED 10 and the remote monitoring device 100 mayeach be equipped with short-range communication circuitry forshort-range PAN communication protocols such as the IOT or BTLE. Inembodiments, the effective communication range of such short-range PANcommunication protocols is consistent with the general proximity of theAED 10 to the physically co-located remote monitoring device 100covering a range for effectively monitoring acoustical tones 104 that anAED 10 emits. In some the status of communication channels between theremote monitoring device 100 and either or both the AED 10 and thecentralized monitoring server/system can also be monitored and canreport an indication to the centralized monitoring server/system thatthe remote monitoring device 100 is functional and in positioned inclose enough proximity to the AED 10 so as to be able to receive areadiness signal, such as from a audible tone and/or from a local NFC orRFID communication.

The housing 102 can include an aperture 106, for example, that can beused for facilitating attachment to the AED 10 and/or be held in closeproximity to the AED. This can be done with the aid of a zip-tie, clip,string, hook and loop fastening member or any other coupling structureto the handle or other convenient feature on the AED 10. Attaching theremote monitoring device 100 to an AED 10 or other feature in closeproximity to the AED can be done in many different ways and attachmentvia the aperture 106 should not be deemed to be limiting. In someembodiments, the remote monitoring device 100 may be affixed to the AEDsuch that the remote monitoring device 100 can be stored within a carrycase, cabinet or other suitable storage location for an AED 10 and/orother medical equipment. Such a carry case, cabinet or other locationcan provide a storage location for optimum placement for detection of anAED self-test beep and provide protection to the monitor when deployedin the field with the AED 10. Placement of a remote monitoring device100 such that it is affixed to an AED 10 near a beep emitting speakercan help ensure optimum performance. In some embodiments, the remotemonitoring device 100 may not actually attach to the AED, but instead bestored within a carry case, cabinet or other location for an AED 10and/or other medical equipment.

In some embodiments, the remote monitoring device 100 may largely betreated as a communication tag for external AED 10 attachment. Noparticular structure or alignment of attachment location of the remotemonitoring device 100 relative to the AED 10 is necessary. Rather, anystructure or arrangement within the proximity of the AED 10 such thataudio sounds 104 can be detected may be sufficient for the remotemonitoring device 100 to be able to report on the functional status ofthe AED 100. This allows for considerable flexibility with regards toplacement and/or attachment of the remote monitoring device 100 and evenpotential use with a variety of models, types, or brands or AEDs andsimilar devices, in some embodiments. Likewise, other embodiments of aremote monitoring device 100 may include a monitoring device integratedwithin an AED carrying case itself, a monitoring device within an AEDwall mount (e.g., medical equipment cabinet), a monitoring device withinan AED communication station, a monitoring device included as part of anAED accessory (electrode pad, CPR assist device, or resuscitationsupplies, etc.), or external security device. In some embodiments it maybe thin, small, or otherwise discrete in profile. Other embodiments maybe larger in size if necessary.

FIGS. 2A and 2B each shows a hardware architecture diagram 101 of oneillustrative embodiment of a remote monitoring device 100. The remotemonitoring device 100 includes a processor 110 operably coupled with: acommunication module 112, a microphone 114, an amplifier and bandpassfilter 116, a detector 118, a speaker 120, a microphone 122, a memory124, and an accelerometer 126. Also shown for powering the processor 110and communication module 112 are batteries 128 and a boost converter130. Further, operably coupled with the microprocessor 110 is an antenna132 for short-range PAN wireless communications protocols such as BTLEor IOT, LEDs 134, a user button 136, and a programming port 138.

Processor 110 can represent at least one processor. In some embodiments,multiple processors or combinations of processing components arecontemplated. One example of a processor is a Nordic Radio NRF52832processor which is an Advanced RISC Machine (ARM)-based System on Chip(SOC) with a Bluetooth radio as a primary on-chip peripheral. Variousother processors are contemplated as well.

Communication module 112 may be a wired or wireless communicationmodule. Depicted in FIGS. 2A and 2B are exemplary options of a wirelessLAN Internet (Wi-Fi) communication module 140A, a WAN Internet(cellular) communication module 140B, and/or a WAN satellitecommunication module 140C, and a wireless IOT network communicationsmodule 142A and/or BTLE communications module 142B configured forshort-range communication protocols. Communication module 112 may serveas the primary wireless connection for the remote monitoring device 100to the Internet in some embodiments, or from the AED 10 to the Internetvia the remote monitoring device 100 in other embodiments. Thecommunications module 112 can send messages to a cloud-based server. AWi-Fi communication module 140 can wirelessly connect to a router or,alternatively, an IOT network communication module 142 can wirelesslyconnect to a gateway. Other suitable communication protocols notexpressly described above may be employed by the remote monitoringdevice.

Microphone 114 can be a low power analog microphone in some embodiments.Such an analog microphone 114 can be considered a first audio sensor 144in some embodiments and work together with a combination of amplifierand bandpass filter 116, a detector (comparator) 118, and other relatedcircuitry that comprise a first audio detection circuitry 146. Thesecomponents can be used to produce an interrupt to power on or otherwisebe activated from a standby mode to the processor 110 when the amplitudeof the audio sound signal detected from audio sounds 104 is above apredetermined threshold. The analog signal chain can have its ownvoltage domain which can be turned on and off to conserve power in someembodiments. In certain embodiments, the first audio sensor 144 couldalternatively be a low power digital sensor and first audio detectioncircuitry 146 could be a digital circuitry as well.

Speaker 120 can be a piezo speaker in various embodiments, althoughother types of speakers can be used as well. The speaker 120 cangenerate an audio tone for a self-test of the remote monitoring device100 itself. The digital speaker 120 can provide high quality digitalaudio via a Pulse Density Modulation (PDM) interface. The PDM interfacecan enables input of pulse density modulated signals from the externaldigital microphone. Input of data is supported by, and data can betransferred to, the processor 110, for example.

Microphone 122 can be a digital microphone. A digital microphone 122 canserve as a second audio sensor 148 in some embodiments. Further, thedetection circuitry associated with the digital microphone 122 can bereferred to as a second audio detection circuitry 150 in variousembodiments. Second audio detection circuitry 150 can include a varietyof other types of forms as well.

As discussed above, having a second microphone or audio sensor, such assecond audio sensor 148 is generally distinguishing over priormonitoring devices which are known to rely on a single audio sensor. Byusing two separate audio sensors, this allows the first audio sensor tobe one of low power consumption and can be used to as a gatekeeper.Specifically, the first audio sensor restricts use of the second audiosensor, which is more accurate but requires considerably more power, toinstances where an initial set of signal criteria are met by audiosounds detected by the first audio sensor. In this arrangement, nuisancenoises that are detected and which clearly to not match the criteria ofan AED sound or signal can be dismissed without have to expendsignificant amounts of battery power. The power consumption savings fromthis arrangement, allows the battery of the remote monitoring device tohave sufficient power for years of use without the danger of batterydepletion. In various embodiments, a battery life of at least four yearscan be expected from such an arrangement. The long-term reliability ofsuch an arrangement provides significant advantages over priormonitoring devices.

Memory 124 can include a serial flash memory IC, for example, in someembodiments and can be used to save configuration settings and firmwareupgrades such as binary file. Further, the memory 124 can be used to logdata.

Accelerometer 126 can optionally be present in various embodiments ofthe remote monitoring device 100 in order to generate an interruptsignal causing the processor 110 to power on or otherwise be activatedfrom a standby mode in response to detected motion. This can beadvantageous as it can provide an indication that the AED 10 is about tobe used. In one example, a bystander who witnesses a medical event anddecides to obtain an AED would pick-up and move the AED prior to itsuse. The movement detected by the accelerometer could generate a signalto be sent to the processor(s) which causes the processor(s) to poweron. Similarly, in another example, just prior to use, an AED could beremoved from a wall case where it resides in an upright location.Reorienting the upright AED to an orientation largely horizontallyresting against the ground could be a movement detected by theaccelerometer that could generate a signal to be sent to theprocessor(s) and causes them to power on. This type of monitoring andcommand to power on or activate from a standby mode can be in additionto the audio sounds monitoring and commands to power on or activate froma standby mode primarily described in this disclosure.

Batteries 128 shown in FIGS. 2A and 2B represent an onboard power sourcefor the remote monitoring device 100. In various embodiments, the remotemonitoring device 100 can be powered by two AA cells, although otherpower sources may be employed (e.g., other types/sizes of batteries,rechargeable batteries, power supply, etc.). The coupled boost converter130 can be used to generate a stable voltage (e.g., 3.3 volts) for theWi-Fi communication module 140 and IOT network communications module142, for example. In alternate embodiments, the remote monitoring device100 can be line-powered or powered by different battery arrangements.

Antenna 132 is present for PAN short-range communications, such as BTLEfor example. BTLE communications are those of a wireless personal areanetwork technology similar to Bluetooth. BTLE communications permit asimilar communication range to be used as Bluetooth but provide asignificant reduction in power consumption required. Communicationsusing this antenna 132 can be useful in the initial provisioning andsetup of the remote monitoring devices 100. In some embodiments, thedigital listening state can monitor audible signals from the AED,one-way short-range PAN wireless signals from the AED, or a combinationof both, including in various embodiments configured to monitor bothsignals for confirmation and/or verification of one or both of wakeupsignals or status signals to reduce false positive alerts.

LEDs 134 and single user button 136 may generally represent asubstantial portion of the user interface for the remote monitoringdevice 100. One or more LEDs 134 are possible and may be bi-color invarious embodiments. Various communication and alerts are made possiblewith these lights.

Programming port 138 is used for debugging and programming of the remotemonitoring device 100. Specifically, the port 138 allows softwaredevelopment and programming of the processor 110.

FIGS. 3A and 3B generally depicts an illustrative embodiment of thepresent disclosure, showing a diagram of a system 151 for remotemonitoring and the associated communications network 160. Shown in thisfigure are a plurality of AEDs 10 (individually shown and referred to attimes with reference numerals 10A, 10B, and 10C here) as well as acorresponding, co-located and attached remote monitoring device 100(individually shown and referred to at times with reference numerals100A, 100B, and 100C here). Each remote monitoring device 100 has thecapability to detect the audio sounds 104 in the form of acousticaltones that an AED 10 emits when it requires service.

The remote monitoring devices 100 also have the capability to wirelesslyconnect to a router 170 (for Wi-Fi based remote monitoring devices 100Aand 100B, for example) or a gateway 172 and associated server 172A (forIOT network based remote monitoring devices 10C, for example) to sendmessages to a cloud-based remote monitoring device server 174 (such ason Amazon® Web Services (AWS), for example). The remote monitoringdevice server 174 handles the transactions with each remote monitoringdevice 100, maintains a remote monitoring device database, and exchangesmessages between a centralized monitoring service or server 176 and theAED remote monitors 100. Monitoring service or server 176 provides aproprietary back end that coordinates AED kit data. Monitoring serviceor server 176 maintains the status of the AEDs 10 and can pushnotifications 178 to the appropriate stakeholders or users 180 asnecessary.

In some embodiments, the server 176 can be embodied by a centralizedmonitoring server and monitoring service, for example. Other servers,services and systems and tools are possible as well. The embodimentrelated to the particular centralized monitoring server described hereinis not limiting. Existing centralized monitoring servers and monitoringservices have been developed for managing various AED services. Theseservices can provide functionality like scheduling, ordering ofsupplies, and even payroll information functions for educators, andemail/text/phone messaging to AED owners in the field. This isfacilitated by the software and applications providing a user interfaceto AED owners. External inputs, such as remote monitoring devicemessages via Wi-Fi, can be routed to the server 174, then routed to theserver 176 for storage and response management. At times, server 176will also be referred to as a monitoring service, centralized monitoringservice, centralized monitoring server, or remote management server.

Further, seen in FIGS. 3A and 3B is a mobile device 182. Mobile device182 can be a phone, tablet, or other range of appropriate electronicdevices. Mobile device 182 provides a separate communication link to theremote monitoring devices 100 that can be utilized in the provisioningprocess for the remote monitoring devices 100 and corresponding AEDs 10,and will be described later in greater detail.

As understood from an example scenario shown in FIG. 4, the structurefor the listening algorithm utilized by the remote monitoring device 100helps determine how the device and its related systems function. Toillustrate this, FIG. 4 shows a diagram 200 of an audio circuit andactive listening timing, according to an embodiment. Lines indicative ofevents are shown adjacent one another on the timing diagram and includerepresentations of: AED beeps at 202; nuisance noises at 204; a firstaudio detection circuitry 146 powered on at 206, an audio wakeupinterrupt at 208; an active listening algorithm 210; and an indicationof when a transmission of the remote monitoring device 100 starts at212.

In the example embodiment illustrated, a first audio detection circuitry146 can be analog and operably connected to a first analog audio sensor144 and processor 110. Further, a second audio circuitry 150 can bedigital and operably connected to a second audio sensor 148 that isdigital.

Note that in alternate embodiments, other audio sensor configurationscould be possible as well. For example, the audio sensors may notnecessarily need to be a combination of analog and digital microphone.The remote monitoring device 100 could instead rely on two digitalmicrophones, three microphones, or other combination of audio sensors.

Initially, the remote monitoring device 100 will duty-cycle power to thefirst audio detection circuitry 146 according to a listening intervalconfiguration setting providing a predetermined detection interval 220to conserve power (such as between 2-240 minutes, 5-120 minutes, 10-60minutes, 30 minutes). Other configurable listening intervals arecontemplated as well. In some embodiments, the detection interval periodis a constant such that, once set, there is no need to have thedetection interval updated or compared to a clock value which caneliminate the power needs for a separate clock circuit component. Asseen at line 206 in FIG. 4, the remote monitoring device 100 can turn onthe first audio detection circuitry 146 for a listening interval 221.The listening interval may be configurable and set according to aparticular amount of time (such as between 10-120 seconds, 20-60seconds, 30-50 seconds, 35 seconds, etc.). In various embodiments, thelistening interval is generally less time than the detection interval(such as on the order of seconds for the listening interval versusminutes for the detection interval). In various embodiments, thedetection intervals and/or the listening intervals may be set so thatthe periods are long enough to catch initial and subsequent beeps orqualifying audio tones, but not so long as to drain battery energyunnecessarily. In various embodiments, the relationship between a periodof the detection interval and a period of the listening interval isgenerally corresponding such that a longer listening interval is usedfor a longer detection interval and a shorter listening interval is usedfor a shorter listening interval.

The first audio detection circuitry 146 generates a wakeup notificationsignal 222 when it detects audio sounds during the predetermineddetection interval 220. This is shown at 208 in FIG. 4. The second audiosensor 148 is powered on in response to the wakeup notification signal222 and commences an active listening mode with an audio listeningalgorithm 210 to provide digital audio signals to the processor 110. Ifthe algorithm 210 does not qualify the audio as an AED beep/tone, thedigital microphone 122 will be powered off. If a qualified beep/tone isdetected, the digital microphone 122 will be muted for a time interval223 which may be, for example, dependent on the AED Model (for example,this could be a precise time between 25 and 35 seconds for a CardiacScience® G3 AED and a different precise time between 25 and 35 secondsfor a Cardiac Science® G5 AED), and will remain on for up to anadditional interval of precise time period to attempt to detect andqualify a second beep. In some embodiments, this additional interval canbe a time period (such as between 4.0-6.0 seconds, 4.0-5.0 seconds,4.6-5.0 seconds, 4.8 seconds, etc.). If a qualifying second beep/tone isdetected, the digital microphone 122 will remain on up to anotherlistening interval to look for a third qualifying tone. In someembodiments, this listening interval may be configurable and setaccording to a particular amount of time (such as between 10-120seconds, 20-60 seconds, 30-50 seconds, 35 seconds, etc.).

In general, the processor 110 is configured to power on in response tothe wakeup notification signal 222, process the digital audio signals,and transmit a signal to the monitoring service 176 to report acondition of the AED 10 based on the digital audio signals that areprocessed. In other embodiments, the digital listening state can alsomonitor one-way short-range PAN wireless signals from the AED, or acombination of both PAN wireless and digital audio signals, including invarious embodiments configured to monitor both signals for confirmationand/or verification of one or both of wakeup signals or status signalsto reduce false positive alerts.

Described another way, the second audio circuitry 150 can be understoodto include an audio listening algorithm 210 that is initiated when anaudio wakeup interrupt 208 occurs. In some embodiments, the second audiosensor 122 (digital microphone) can stream 16 kHz PDM data into 128sample buffers which are processed by the audio listening algorithm 210.This processing can include the output of a decimator being compared toan adaptive threshold, and pulse timing characteristics being computedbased on the time the signal is above the threshold. In an embodiment asdescribed more fully below in connection with the description of FIG. 5,the audio listening algorithm 210 identifies the presence of threeconsecutive qualifying pulses. Pulses are qualified based on criteria orqualification parameters such as pulse width and pulse interval. Otherpulse qualification parameters could be utilized as well such asfrequency, amplitude, intensity, or other waveform features.

In various embodiments, the number of qualified pulses can be configuredto be three or more pulses that meet the same pulse qualificationparameters, and in other embodiments, the number of qualified pulses canbe configured to be a consecutive sequence of one or more pulses thatmeet a different set of qualification parameters for differentpositioned pulses in a sequence of at least two pulses or of at leastthree pulses. The qualification criteria or qualification parameters ofthe pulses may be different for different models of AED 10 and may beset based on a model type communicated to the remote monitoring device100 from the centralized monitoring service or server 176 duringprovisioning or initialization. Accordingly, in some embodiments, adevice is contemplated having a listening structure where a first audiodetection circuitry 146 powers on, or otherwise activates from a standbymode, a second audio detection circuitry 150 to trigger a transmissionreport and determine that an audio beep detected is qualifyingSpecifically, a remote monitoring device 100 can monitor and manage by amonitoring service (such as centralized monitoring service or server 176with a database via a communications network 160, for example) acondition of an AED 10 (such as whether service is required) based onaudio signals from the AED 10. The remote monitoring device 100 includesa housing 102 that is configured to be positioned outside of the AED 10such that audio sounds 104 from the AED 10 can be detected. The housing102 contains at least one processor 110, a communications module 112, afirst audio sensor 144, a first audio detection circuitry 146, a secondaudio sensor 148, and a second audio detection circuitry 150. In someembodiments, the first audio sensor 144 includes an analog microphone114 that detects audio sounds 104 based on an initial audio threshold ofat least one of sound amplitude and/or sound frequency.

In some embodiments, the first audio sensor 144 can be dynamicallymodified to respond to changes in the environment of the AED 10. Forexample, in very loud environments that continue to cause the remotemonitoring device 100 to power on the second audio detection circuitry150 in response to a wake up notification signal 222, but the secondaudio detection circuitry 150 determine that the noises triggering thewake up notification signal are only “nuisance events,” the processor110 can adjust one or both of the time periods for the detectioninterval and/or listening interval in an effort to avoid or reduce suchnuisance events help to conserve power. In some embodiments, theprocessor 110 may evaluate a set of detection intervals to selectivelyadjust detections intervals in an effort to avoid or reduce detectionduring the day and increase detection during the night. In otherembodiments, the processor 110 may be provided with an ability todynamically adjust the initial audio threshold of the analog microphone114 by, for example, writing to a port that adjusts a parameter of themicrophone, an effective equivalent of an input circuit, or a power toan amplifier associated with the microphone.

Additionally, the communications module 112 is operably connected to theat least one processor 110 and configured to transmit electroniccommunications to the monitoring service 176 via the communicationsnetwork. In some embodiments, the communications module 112 isconfigured to wirelessly transmit electronic communications. This can bedone via one of Wi-Fi or IOT network, for example.

Additionally, the first audio detection circuitry 144 can be operablyconnected to the first audio sensor 144 and the at least one processor110. The first audio detection circuitry 146 is configured to power onduring a predetermined detection interval 220 and generate a wakeupnotification signal 222 when the first audio detection circuitry 146detects qualifying audio sounds 104 during the predetermined detectioninterval 220. In some embodiments, the first audio detection circuitry146 is analog.

The first audio detection circuitry 144 is continuously powered separatefrom processor 110 and is of significantly lower power than required byprocessor 110. In general, processor 110 runs based on a first detectionof audio, then qualifies based on more detailed analysis of the signal.

In an alternate embodiment of the design, a digital audio buffer couldbe added to the digital microphone so that when processor 110 turns onbased on analog detection, it can query the digital microphone bufferfor pulses already recorded. This eliminates the need to stay on to waitfor a qualifying pulse. The previous pulse already recorded and storedin digital mic buffer running could then be used without having to turnthe processor 110 on.

The second audio detection circuitry 150 is operably connected to thesecond audio sensor 148 and the at least one processor 110. The secondaudio detection circuitry 150 is configured to power on in response tothe wakeup notification signal 222 and commence an active listening modeto provide digital audio signals to the at least one processor 110. Insome embodiments, the second audio detection circuitry 150 is digital.

In some embodiments, the second audio detection circuitry 150 is able tobe powered on in less than ten milliseconds from a detection ofqualifying audio sounds 104 by the first audio sensor 144 that satisfyan initial audio criteria. In some embodiments, the second audiodetection circuitry 150 is configured to be powered on in less than onemillisecond from detection of audio sounds 104. In some embodiments, thesecond audio detection circuitry 150 is configured to be powered onbetween 0.5 milliseconds and 5 milliseconds from detection of audiosounds 104. In some embodiments, the second audio detection circuitry150 is configured to be powered on between 1 millisecond and 10milliseconds from detection of audio sounds 104. In some embodiments,the second audio detection circuitry 150 is turned on prior tocompletion of an audio sound 104 from the AED 10 initially detected bythe first audio sensor 144, shortly or immediately after, or during asubsequent audio sound 104 from the AED 10. The at least one processor110 is configured to power on the second digital microphone in responseto the wakeup notification signal 222, process the digital audiosignals, and transmit a signal to the monitoring service 176 to report acondition of the AED 10 based on the digital audio signals that areprocessed.

In some embodiments, the signal transmitted to the monitoring service176 identifies a serial number of the AED 10. In some embodiments, theaudio sounds 104 from the AED 10 communicate as part of the message, atleast one of the following: a self-test failure of the AED 10; a batteryexpiration; and an electrode expiration. Self-test failures can includefailures of internal electronics, buttons, a CPR feedback device, a highvoltage circuit (including standard, partial or full energy charge cycletests of this), and other battery and/or electrode tests, for example.

In some embodiments, the audio sounds 104 from the AED 10 includesinformation based an encoding scheme, and the processor(s) 110 isconfigured to analyze the digital audio signals to cause the signaltransmitted to the monitoring service 176 to include status informationof the AED 10 based on the encoding scheme. In some embodiments, the AEDcould embed additional information in the audible tone by usingdifferent pulse widths and/or intervals to convey specific types oferrors, rather than just a generic error has occurred. This encodingscheme could include a frequency shift keying (FSK) technique, forexample. This would provide additional information of the error (code),as well as improved Signal to Noise Ratio (SNR). The enhanced SNR couldthen provide for greater rejection of unqualified audible events usingthe specificity provided with embedded data codes (vs. just usingamplitude, etc.). Other encoding schemes could include encoding thatvaries inter-beep or inter-pulse timing and length to help determine thetype of failure (i.e. self-test, battery expiration, electrodeexpiration, etc.). Similarly, encoding could be done with a quasi-morsecode option in which various beep codes are conveyed. In someembodiments, encoding may be non-audible. Beeps could be designed tohave good selectivity and ability to reject noise. In some embodiments,the amplitude of signals could be fine-tuned to provide informationabout certain high priority alarms. An alarm indicating an AED is unableto perform a rescue could increase amplitude and allow people to hearthe alarm clearly. In some embodiments, cadence and volume of beep couldbe used to encode a level of concern and urgency into the signals.

In some embodiments, the at least one processor 110 is furtherconfigured to power down once the signal is transmitted to themonitoring service 176. Likewise, in various embodiments, the processor110 can be configured to power down if any of a variety of conditions isnot met. Conditions could include that a first qualifying tone is notdetected in the digital audio signals during a first active listeninginterval; a second qualifying tone is not detected in the digital audiosignals during a second active listening interval; or a third qualifyingtone is not detected in the digital audio signals during a third activelistening interval.

As discussed above, in some embodiments, power consumption necessary foroperation of the first audio detection circuitry 146 is less than powerconsumption necessary for operation of the second audio detectioncircuitry 150. Accordingly, relying on low power consumption for basicinitial detection and operation of the remote monitoring device 100,enables extended battery life and a device that does not requirefrequent power source replacement. The advantages to such extendedbattery life can be significant as the long-term reliability of theremote monitoring device 100 is largely only limited by battery drainover time.

Accordingly, in some embodiments, a device is contemplated having aprocessor 110 actively control the remote monitoring device components.In some such embodiments, a first audio detection circuitry 146 signalsa second audio detection circuitry 150 to wake up and confirmappropriate sound detection and trigger a transmission report.Specifically, a remote monitoring device 100 for monitoring audiosignals from an AED 10 and electronically reporting to a monitoringservice 176 via a communications network 160 is contemplated. The remotemonitoring device 100 includes a housing 102 configured to be positionedoutside of the AED 10 such that audio sounds 104 from the AED 10 can bedetected. The housing 102 contains a communications module 112, a firstaudio sensor 144, a first audio detection circuitry 146, a second audiosensor 148, a second audio detection circuitry 150, and at least oneprocessor 110.

Additionally, the communications module 112 is configured to transmitelectronic communications to the monitoring service 176 via thecommunications network 160. The first audio detection circuitry 146 isoperably coupled with the first audio sensor 144. The first audiodetection circuitry 146 is configured to detect audio sounds 104 fromthe AED 10 via the first audio sensor 144. The second audio detectioncircuitry 150 is operably coupled with the second audio sensor 148. Thesecond audio detection circuitry 150 can be configured to detect theaudio sounds 104 from the AED 10 via the second audio sensor 148. The atleast one processor 110 is operably coupled with the communicationsmodule 112, the first audio detection circuitry 146, and the secondaudio detection circuitry 150.

Accordingly, in some embodiments, a device is contemplated having alistening structure where audio detection circuitry listens for a firstsignal (to wake up), a second signal (to confirm the signal from the AED10), and third signal (to confirm the signal from AED 10 again, andtrigger a transmission). Specifically, a remote monitoring device 100 iscontemplated for monitoring audio signals from an AED 100 andelectronically reporting to a monitoring service 176 via acommunications network 160. The remote monitoring device 100 includes ahousing 102 configured to be positioned outside of the AED such thataudio signals from the AED 10 can be detected. The housing 102 containsa communications module 112, at least one audio sensor (i.e. 144 and/or148), at least one audio detection circuitry (i.e. 146 and/or 150), andat least one processor 110. The communications module 112 is configuredto transmit electronic communications to the monitoring service 176 viathe communications network 160.

The at least one audio detection circuitry (i.e. 146 and/or 150) isoperably coupled with the at least one audio sensor (i.e. 144 and/or148). The at least one audio detection circuitry (i.e. 146 and/or 150)is configured to detect audio sounds 104 from the AED 10 via the atleast one audio sensor (i.e. 144 and/or 148). The at least one processor110 is operably coupled with the communications module 112 and the atleast one audio detection circuitry 146. Further, the at least oneprocessor 110 is configured to: process signals from the at least oneaudio detection circuitry 146 based on the detected audio sounds 104;detect a first audio signal from the processed signals; in response tothe first audio signal being detected, commence an active listening modeto detect a second audio signal from the processed signals and confirmthat the second audio signal meets a predetermined criterion associatedwith the active listening mode; in response to the second audio signalbeing detected, re-commence the active listening mode to detect a thirdaudio signal from the processed signals and confirm that the third audiosignal meets the predetermined criterion associated with the activelistening mode, and transmit a report signal to the monitoring service176 if the third audio signal meets the predetermined criterion.

In some embodiments, the predetermined criterion associated with theactive listening mode is different than at least one criteria used bythe at least one audio detection circuitry (i.e. 146 and/or 150) todetect qualifying audio sounds 104 from the AED 10. In some embodiments,the predetermined criterion associated with the active listening modeare based on at least one of: a pulse width, a frequency, an amplitude,and a pulse interval, of each tone in the audio signals. In someembodiments, the at least one audio sensor (i.e. 144 and/or 148) mutesfor an interval during the active listening mode between the secondaudio signal and the third audio signal. In various embodiments, the atleast one processor 110 is configured to power down if the second audiosignal does not meet the predetermined criterion or if the third audiosignal does not meet the predetermined criterion.

In addition to the capability to detect the audio sounds 104 in the formof acoustical tones that an AED 10 provides, in some embodiments, theremote monitoring device 100 further includes an optical sensor (notshown) operably connected to the at least one processor 110 to detectwhether the AED 10 presents a visual indication of an AED self-testfailure. For example, the optical sensor can detect whether a light onthe AED 10 is illuminated to indicate an AED self-test failure.

In some embodiments, increases in an amplitude of the audio sounds 104from the AED 10 are used to convey a level of urgency to be included inthe signal transmitted to the monitoring service 176. In someembodiments, an audio sound 104 from the AED 10 is outside an audiblerange of human hearing. In some embodiments, an audio sound 104 from theAED 10 includes variations in at least one of: an inter-tone timing, anda length, of the audio sounds 104 that are used to convey information tobe decoded by the processor(s) 110. In other embodiments, different setsof one-way short-range PAN wireless signals from the AED 10 may be usedto convey information to be decoded by the processor(s) 110.

FIG. 5 sets forth a flow diagram 300 of operations for the remotemonitoring device 100 and some of its various functional modes. Thesemodes are generally areas of functional responsibility and relate toareas covered in the FIGS discussed this far. This includes monitoringaudio sounds 104 (via audio sensor(s) 144 and 148 and audio detectioncircuitries 146 and 150), monitoring AED motion (via an accelerometer126), performing a self-test, and communicating results to a monitoringservice 176 through a remote monitoring device server 174. Accordingly,FIG. 5 provides a high-level overview of the modes/states of the remotemonitoring device 100 and related methods and systems in performance ofoperations.

When initially deployed with an AED 10, the remote monitoring device 100undergoes provisioning and related operations. This is represented inFIG. 5 by provisioning mode 302, ship mode 304, and self-test mode 306boxes on the diagram 300. In terms of provisioning, it should be firstunderstood that to set up the system, a mobile application 310 runningon a mobile device 182 connects to the remote monitoring device 100 viaa Bluetooth link 132. (See FIGS. 3A-3B). The mobile device 182 alsoconnects to the centralized monitoring service 176 via a Wi-Fi data link311 or cellular data link 313 or IOT network link 315. (See FIGS.3A-3B). In embodiments, the remote monitoring device 100 may also beprovided with WAN cellular communication module 142 to enable connectionvia a cellular data link 313 to the centralized monitoring server 176. Auser will use the mobile application to select an AED kit on thecentralized monitoring service 176 and associate (i.e. pair) it to theproximate remote monitoring device 100 and enter the location of theseas an AED kit. The mobile application 310 is also used to configureWi-Fi based remote monitoring devices 100 with site-specific parameters,such as network IDs and security credentials using the Bluetooth link312. In embodiments, the remote monitoring device 100 with connection tothe centralized monitoring server 176 via an IOT network connection(172, 172A) using the Bluetooth link 312 or similar short-range PANnetwork communication protocols such as NFC. In any of the communicationchannels modes, the remote monitoring device may report AED status,site-specific parameters and/or communication channel status.

Another aspect of the provisioning process involves the self-test mode306. Following set-up, the remote monitoring device 100 attempts toconnect to the centralized monitoring service 176 to download the commonconfiguration parameters. The mobile application 310 and/or remotemonitoring device 100 will indicate the success or failure of theconnection. The self-test mode 306, provisioning mode 302 and relatedmodes and operations will be described later in greater detail inassociated with subsequent figures.

Once provisioned, the remote monitoring device 100 may reside in a lowpower sleep mode 314. Very little power is expended while in this mode.Upon expiration of a listening timer based on a predetermined detectioninterval 220, the device transitions to an analog detection mode 316. Ifno audio sounds 104 are detected to generate a wakeup signal, the device100 returns to the low power sleep mode 314. If, however, an audio sound104 is detected during the predetermined detection interval 220 of theanalog detection mode 316, the device 100 will transition to a digitallistening mode 318 (also referred to at times as active listening mode).If there is no detection of qualifying audio sounds 104 based onprocessed digital audio signals, the device 100 returns to the low powersleep mode 314. If, however the digital audio signals processed indicatea condition of the AED 10 that requires transmission, the remotemonitoring device 100 enters a transmission mode 320. In thetransmission mode 320, a signal is transmitted to the centralizedmonitoring service 176 to report the AED condition. Once thistransmission is completed or fails, the remote monitoring device 100returns to the low power sleep mode 314. Also referenced in FIG. 5, is aself-test mode 322 that can be utilized in response to a short buttonpress or a 24-hour timer. Successful self-test modes 322 will result innotification via transmission mode 320.

Accordingly, in some embodiments, a device is contemplated having alistening structure where a processor has a low power sleep state(including low power sleep mode 314), a detection state (includinganalog detection mode 316), a listening state (including digitallistening mode 318), and a transmission state (including transmissionmode 320). Specifically, a remote monitoring device 100 for monitoringaudio signals from an AED 10 and electronically reporting to amonitoring service (such as centralized monitoring service 176 via acommunications network, for example) is contemplated. The remotemonitoring device 100 includes a housing 102 configured to be positionedoutside of the AED 10 such that audio signals from the AED 10 can bedetected. In various embodiments, the housing 102 contains at least oneprocessor 110, a communications module 112, a first audio sensor 144, afirst audio detection circuitry 146, a second audio sensor 148, and asecond audio detection circuitry 150.

Additionally, the communications module 112 is operably connected to theat least one processor 110 and is configured to transmit electroniccommunications to the monitoring service 176 via the communicationsnetwork 160. In various embodiments, the first audio detection circuitry146 is operably connected to the first audio sensor 144 and the at leastone processor 110, and the second audio detection circuitry 150 isoperably connected to the second audio sensor 148 and the at least oneprocessor 110.

The at least one processor 110 is configured to: reside in a low powersleep state (or low power sleep mode 314) by default; commence adetection state (i.e. analog detection mode 316) for wakeup confirmationduring a detection interval 220 in which the first audio detectioncircuitry 146 is configured to power on and generate a wakeupnotification signal 222 when the first audio detection circuitry 146detects audio sounds 104 during the detection interval 220 via the firstaudio sensor 144; commence a listening state (i.e. digital listeningmode 318) for alert confirmation in response to the wakeup notificationsignal 222 in which the second audio detection circuitry 150 isconfigured to power on and provide digital audio signals to the at leastone processor 110 in an active listening mode (i.e. digital listeningmode 318); and commence a transmission state (i.e. transmission mode320), upon confirmation of at least three consecutive qualifying tonesin the audio signals detected in corresponding qualifying intervalsduring the digital listening state (i.e. digital listening mode 318), inwhich the communications module 112 is caused to transmit a message tothe monitoring service 176 via the communications network 160 indicatinga status of the AED 10.

In some embodiments, the transmission state (i.e. transmission mode 320)further includes powering down the second audio detection circuitry 150once the communication module 112 is caused to transmit a message to themonitoring service 176.

FIG. 6 shows a self-test operation diagram 400 for the remote monitoringdevice 100 itself. This self-test of the remote monitoring device 100 isindependent of any self-tests run by the AEDs 10 that are beingmonitored. Lines indicative of events are shown on a common chart andinclude representations of: audio sounds 104 such as beeps of the remotemonitoring device 100 at 402; the audio circuit of the first audiodetection circuitry 146 at 404; an audio wakeup interrupt at 406; anactive listening algorithm of a second audio detection circuitry 150shown at 408; and an indication of when a transmission of the remotemonitoring device 100 occurs at 410.

In the embodiment depicted, the self-test is initiated at 412 via a24-hour timer started at the time the remote monitoring device 100 isinitially provisioned, or by a button press by a user at a later time.The self-test first tests the first audio detection circuitry 146 (i.e.analog audio circuit) by generating a speaker 120 (piezo beeper) tone104 and confirming an audio wakeup interrupt at 406 occurs. Theself-test then tests the second audio detection circuitry 150 (i.e. thedigital active listening circuit) by generating a speaker 120 (piezobeeper) tone 104 and confirming the pulse amplitude and duration aresufficient for detection. In some embodiments, a beeper/audio sound 104is sufficient if within a determined frequency (i.e., between 3-5 KHz,3.5-4.5 KHz, or 4 KHz) and/or a determined pulse width (i.e. between200-400 ms, 250-350 ms, or 300 ms), for example. As shown, an interval414 is present between tones 104. This interval 414 may be between 2-4seconds, 2.5-3.5 seconds, or 3 seconds, for example. Also depicted, amute interval 416 for the active listening algorithm is present. Thismute interval 416 may be between 2-4 seconds, 2.5-3.5 seconds, or 3seconds, for example.

The self-test of the remote monitoring device 100 also measures thebattery voltages under load of radio transmission. The battery 128 istested during every transmission and self-test looks at the batterystatus from the previous transmission. A low battery status is definedas a voltage under 2.2 V. The results of the self-test are stored inmemory 124 and a result code for the self-test is transmitted to thecentralized monitoring service 176.

Accordingly, various embodiments contemplate a device having a self-testfeature. Specifically, a remote monitoring device 100 is disclosed formonitoring audio signals from an AED 10 and electronically reporting toa monitoring service (such as centralized monitoring service 176 via acommunications network 160, for example). The remote monitoring device100 includes a housing 102 configured to be positioned outside of theAED 10 such that audio signals from the AED 10 can be detected. Thehousing 102 contains at least one processor 110, a memory 124, acommunications module 112, a speaker 120 (such as a piezo speaker insome embodiments), at least one audio sensor 144, and at least one audiodetection circuitry (i.e. 146 and/or 150). The memory 124 is operablyconnected to the at least one processor 110.

The communications module 112 is operably connected to the at least oneprocessor 110 and configured to transmit electronic communications tothe monitoring service 176 via the communications network 160. Thespeaker 120 is operably connected to the at least one processor 110 andconfigured to generate audio sounds 104 as part of a self-test of theremote monitoring device 100. The at least one audio detection circuitry(i.e. 146 and/or 150) is operably coupled with the at least one audiosensor 144.

Additionally, the at least one audio detection circuitry (i.e. 146and/or 150) is configured to detect audio sounds 104 via the at leastone audio sensor 144 and provide digital audio signals to the at leastone processor 110. The at least one processor 110 is configured to:periodically cause the speaker 120 to generate the audio sounds as partof the self-test of the remote monitoring device 100; receive thedigital audio signals to confirm that the audio sounds 104, as part ofthe self-test of the remote monitoring device 100, originate from thespeaker 120; and transmit a message conveying results of the self-testof the remote monitoring device 100 to the monitoring service 176 viathe communications network 160.

In some embodiments, the at least one audio detection circuitry (i.e.146 and/or 150) is configured to power on during an analog detectioninterval 220 and generate a wakeup notification signal 222 when audiosounds 104 are detected during the analog detection interval 220. Insome embodiments, the at least one audio detection circuitry 146 isconfigured to power on in response to the wakeup notification signal 222and commence an active listening mode.

In some embodiments, the housing 102 includes a battery 128 ofindeterminate life operably connected to the processor(s) 110 and thecommunications module 112. In some embodiments, the self-test is furtherconfigured to measure a battery voltage of the battery 128 under loadduring at least two successive transmissions by the communicationsmodule 112 to determine if a low battery status is present. In someembodiments, the processor(s) 110 can cause the communications module112 to provide information related to battery status from the previoustransmission. In some embodiments, the self-test is configured to beconducted daily in response to one of a 24-hour timer or physical pressof button 136 of the remote monitoring device 100.

FIGS. 7 and 8 show diagrams 500A and 500B of the communications flow forconfiguring/provisioning Wi-Fi and IOT Network remote monitoring devices100, respectively. FIG. 7 shows a diagram of the communications flow fora Wi-Fi module 140 in a system for AED remote monitoring. As shown, auser 502, remote monitoring device 100, mobile application 310 andremote monitoring service 176 are spaced horizontally across thediagram.

As understood from FIGS. 7 and 8, provisioning remote monitoring device100 supports firmware upgrades to the device 100, configures the remotemonitoring device 100 to enable communication with the remote monitoringdevice server 174, enters remote monitoring device data (identificationand configuration) on the centralized monitoring service 176 and, if theremote monitoring device 100 is new, adds the remote monitoring device100 to an AED kit. The centralized monitoring service 176 may direct newdata to be written into the flash memory 124 of the remote monitoringdevice 100.

The process begins when the user 502 turns on the mobile application 310at 504 and navigates to the provisioning screen of the remote monitoringdevice 100 at 506. The user 502 also presses the button 136 on theremote monitoring device 100 for an extended period of time, such asfour seconds or longer (ten seconds in some embodiments) at 508. Thiscauses the remote monitoring device 100 to send out its Bluetoothadvertisement at 510 and the mobile application 310 connects to theremote monitoring device 100 over Bluetooth at 512 and retrieves theremote monitoring device's firmware version. If the remote monitoringdevice firmware version is different from firmware revision available inmobile application 310, provisioning will allow remote monitoring devicefirmware update. If firmware update is selected, the remote monitoringdevice firmware will be updated. New firmware will be installed afterthe mobile application 310 disconnects from the remote monitoring device100, ending the provisioning session.

At this point, two paths are possible in this embodiment: one for aWi-Fi remote monitoring device 100 depicted in FIG. 7 and another for aIOT network remote monitoring device 100 depicted in FIG. 8. For a Wi-Firemote monitoring device 100 in FIG. 7, the mobile application 310commands the remote monitoring device 100 to scan for the SSIDs visibleat 514 and transfers that list of SSIDs to the mobile application 310 at516. The user 502 selects the SSID of the Wi-Fi access point and entersthe password for the Wi-Fi access point at 518; the mobile application310 passes both to the remote monitoring device 100. The remotemonitoring device 100 determines if it can associate with the accesspoint and communicates association status to the mobile application 310at 520. Following a successful association, the remote monitoring device100 is commanded to initiate download of parameters at 522 andcommunicate with the centralized monitoring service 176 toupload/download its configurable parameters at 524. Provisioning is thencomplete and the remote monitoring device 100 will enter self-test andbegin normal operations at 526.

As shown in FIG. 8, the connection for an IOT network remote monitoringdevice 100 is simpler. Following Bluetooth connection, describedpreviously, the remote monitoring device 100 is commanded to transmitand receive data over the IOT network, including the base station 172.Utilizing the IOT network, the remote monitoring device 100 communicateswith the centralized monitoring service 176 to upload/download itsconfigurable parameters at 530. Provisioning is then complete, and theremote monitoring device will enter self-test and begin normaloperations at 532.

In FIG. 9 an architecture diagram 600 of an embodiment of the mobileapplication 310 for the remote monitoring device system is depicted.Specifically, a mobile device 182 is shown that is running the mobileapplication 310. The mobile device 182 further includes: a userinterface 602; Wi-Fi circuitry 604; a camera 606; and Bluetooth enabledcircuitry 608. The Wi-Fi circuitry 604 (or its cellular data connection)is used to connect to the centralized monitoring service 176. The camera606 can be used to scan information codes 610 (i.e. bar codes, QR codes,etc.) on the remote monitoring device 100 and the AED 10 so that theremote monitoring device 100 can be added to the AED kit database in thecentralized monitoring service 176. Bluetooth 508 is used to connect tothe remote monitoring device 100 for configuration of remote monitoringdevice-specific parameters as needed.

FIG. 10 shows a diagram 700 of the remote monitoring data flow at a highlevel for an embodiment of the system. As indicated, both Wi-Fi and IOTnetwork-based AED remote monitoring devices 100 (individually referredto as remote monitoring device 100A and 100C here, respectively) have asimilar high-level function AED remote monitoring devices 100 willinitiate a connection to the AED remote monitoring device server 174 ifit detects an AED self-test error beep. AED remote monitoring devices100 also check-in on a periodic basis, nominally every 24 hours.

The ultimate destination for the AED remote monitoring device data isthe centralized monitoring server 176. The server 176 maintains an AEDremote monitoring device's configuration, which is pushed back to theAED remote monitoring device 100 whenever the AED remote monitoringdevice 100 establishes a connection. The nature of the data-path and theformat of the data are different between a Wi-Fi and IOT network-basedAED remote monitoring devices 100, but the functions and purposes arethe same.

Wi-Fi-based AED remote monitoring devices 100A will establish a logicalconnection (a session) directly to the AWS AED remote monitoring deviceserver 174 and exchange JSON formatted messages. The AED remotemonitoring device server 174 will exchange JSON-formatted messages tothe centralized monitoring server 176. The AED remote monitoring deviceserver 174 will receive from centralized monitoring server 176 the AEDremote monitoring device's configuration which it will then send back tothe AED remote monitoring device 100A.

In various embodiments, IOT network AED remote monitoring devices 100C,on the other hand, will connect to a IOT network server 172A which willsubsequently establish a connection to the AED remote monitoring deviceserver 174 to exchange JSON formatted messages. The API between the IOTnetwork server 172A and the AED remote monitoring device server 174 isnot the same as used by Wi-Fi based AED remote monitoring devices 100primarily due to limitations imposed by the IOT network protocol. In oneembodiment, the IOT network server 172A bundles the 12-byte AED remotemonitoring device payload and IOT network-provided meta-data to the AEDremote monitoring device server 174. The metadata contains information,such as signal strength, and which IOT network base station received theAED remote monitoring device's message. The AED remote monitoring deviceserver 174 interprets/converts the AED remote monitoring device's12-byte payload and exchanges JSON-formatted messages to the centralizedmonitoring server 176. The remote monitoring device server 174 receivesthe AED remote monitoring device's configuration from the centralizedmonitoring server 176 and reformats as necessary before sending it tothe IOT network server 172A which then sends the downlink payload to theAED remote monitoring device 100.

In various embodiments, only one API between the AED remote monitoringdevice server 174 and the centralized monitoring server 176. The AEDremote monitoring device server 174 also extracts and maintains adatabase of the IOT network metadata for future data mining projects.

In various embodiments, switching circuitry 141 as shown in FIG. 2B isincluded as part of the remote monitoring device 100 to enable theremote monitoring device to be more adaptable for different customerfacility configurations depending, for example, on the type of Wi-Finetwork (simple WPA or more complex Enterprise class networks (e.g.,using high end Cisco routers) that may be in the facilities and/orcampuses of a given customer. The more complex the Wi-Fi network, themore coordination of multiple functions may need to be performed by thecustomer to reliably set up the remote monitoring devices 110. In thesesituations, the ability for the remote monitoring device 110 toselectively switch between two or more of the PAN, LAN and WAN networks,for example, can provide both a more flexible and adaptable networkcommunication, as well as a more reliable communication networkconnection if one of the communication channels were to go down for anyreason. In addition, this flexibility can decrease the setup complexityfor complex Wi-Fi networks by using a cellular network instead. Thisflexibility can also reduce false alerts due to failures or powerinterruptions in a customer Wi-Fi access point.

In some embodiments, customers may prefer to set up all of the remotemonitoring devices 110 and corresponding AEDs 10 at the same time in acentral location such as a conference room. This is not recommended,since the Wi-Fi signal strength will be different at the locations wherethe remote monitoring devices 110 are deployed, versus in the centrallocation. In such situations, the actual location of a given remotemonitoring devices 110 and corresponding AED 10 may be manually enteredinto the backend server or via the mobile app, although this can be bothinefficient and error prone and needs to be updated if the remotemonitoring devices 110 and corresponding AED 10 is moved to a differentlocation.

The use of a primary or switchable cellular network for communicationmodule 142 can provide advantages of less reliance on customer support,a single consistent interface that facilitates a common area for setup.In some embodiments, a current location of the the remote monitoringdevices 110 and corresponding AEDs 10 can be determined through cellulartriangulation techniques and that current information can beautomatically determined. In other embodiments, the addition of a GPScircuitry to the remote monitoring device 110 can provide provide evengreater resolution in helping to identify a location of the device 110and AED 10 within a building. In these embodiments, the current locationcan be communicated to the server to eliminate/reduce the need tomanually enter/keep track of the current location of the device 110 andAED 10. In such cellular embodiments, the data/bandwidth required can berelatively low, similar to telemetry applications, which can facilitatethe use of older and cheaper WAN technologies that can have greatercellular network availability and at reduced cost compared to the latestcellular technologies such as 5G.

In some of such cellular-equipped embodiments, the remote monitoringdevice 110 can be configured to communicate with authorized users whoare trained in AED rescues in an emergency situation. In variousembodiments, these authorized users could have their location trackedbased on their own cellphone, for example, such that a device 110 andAED 10 closest to the authorized user could inform it where that device110 and AED 10 is located (either via an interface or notification onthe mobile phone screen or by playing audible prompts). In otherembodiments, this notification feature could be augmented withgeofencing, such that given areas/regions in a building, can beassociated with specific remote monitoring devices 110 correspondingAEDs 10 in relation to the authorized users within a geofenced area.

In some embodiments, a one-way PAN communication between the AED 10 andthe remote monitoring devices 110 is provided to augment/overcomepotential false positive alerts in loud ambient noise environments. Insome embodiments, NFC communication technology in a transmit-onlyconfiguration pairs the AED 10 with the remote monitoring devices 110.Transmit-only for such NFC communication addresses any cybersecurityconcerns as there would be no communication allowed into the AED 10. Inembodiments, the NFC data transmitted could also be encrypted similar toNFC credit card readers to secure proprietary data being sent betweenthe AED 10 and the remote monitoring device 110.

In various embodiments, a plurality of switchable network interfaces areprovided in the remote monitoring device 110, In some embodiments, aplurality of switchable network interfaces are operably connected toswitching circuitry and/or to the one or more processors. Inembodiments, a seamless switching between the networks as a function ofsignal strength, network availability, cost, customer preference, forexample. In various embodiments, a configuration for LAN and/orcellular/satellite WAN interfaces could include, for example, Wi-Fi 6,Wi-Fi 5 GHz, Wi-Fi 2.4 GHz, Cellular 3G, 4G, LTE, 5G, and LEO.Utilization of such a plurality of switchable network interfaces couldimprove the overall network availability and reliability for the remotemonitoring device 110 and monitoring service.

In some embodiments, the remote monitoring device 110 could be providedwith a port to allow for PCMCIA or SIM chip provision of a WANcommunication interface to communicate with LEO satellites. Such LEOinterfaces could provide coverage virtually everywhere and could providea safety net in cases where there is no Wi-Fi and no terrestrialcellular coverage (e.g., maritime or remote environments)

A mobile device 182 running a mobile application 310 is used forprovisioning and configuration of the AED remote monitoring device 100.The mobile application 310 connects to both the AED remote monitoringdevice 100 over a Bluetooth link and to the centralized monitoringserver 176 via Wi-Fi or IOT network. The mobile application 310interfaces with the centralized monitoring server 176 so a user canselect an AED ‘Kit’. In this context, an AED kit is a configuration thataggregates the AED and other elements of the system.

The mobile application 310 uses a Bluetooth link control and AED remotemonitoring device 100 configuration as needed. Wi-Fi-based AED remotemonitoring devices 100 require local configuration for the network ID,and security parameters. AED remote monitoring device configurationitems are entered into the centralized monitoring server 176 and areultimately downloaded by the AED remote monitoring device 100 wheneverit establishes a connection to the AED remote monitoring device server174. More specifically, the AED remote monitoring device's configurationis received from the centralized monitoring server 176 when the AEDremote monitoring device server 174 sends a remote monitoring device'sstatus to the centralized monitoring server 176. The AED remotemonitoring device server 174 then sends the configuration in the replyto the AED remote monitoring device 100 via the IOT network or Wi-Filink. Web browser 702 is present providing an API to the centralizedmonitoring server 176.

Some embodiments relate to a mobile device application 310 and relatedsystems. For example, a system for AED monitoring utilizing a mobiledevice 182 is disclosed. The system includes a mobile application 310and a remote management server such as centralized monitoring server176. The mobile application 310 is configured to be executable on themobile device 182 to receive data about an AED 10 and an AED remotemonitoring device 100. The remote management server (i.e. centralizedmonitoring server 170) is configured to communicate with the mobiledevice 182 and receive data from the mobile device 182. The mobileapplication 310 is executable on the mobile device 182 is configured to:establish a communications connection between the mobile device 182 andthe AED remote monitoring device 100; establish a communicationsconnection between the mobile device 182 and the remote managementserver (i.e. centralized monitoring server 170); receive or obtain alocation of at least one of the AED 10 or the AED remote monitoringdevice 100; use the communications connection between the mobile device182 and the AED remote monitoring device 100 and the location toconfigure the AED remote monitoring device 100 with site-specificparameters; and communicate a notification 178 to the remote managementserver (i.e. centralized monitoring server 170) of an attempt of the AEDremote monitoring device 100 to connect to the remote management server(i.e. centralized monitoring server 170).

Many embodiments are possible with respect to the various systems andmethods described throughout this disclosure. In some embodiments, themobile application 310 is further configured to communicate product dataof the mobile device 182 via camera images of QR codes or barcodes 610on the AED 10 and on the AED remote monitoring device 100 andcommunicate the product data to the remote management server. In someembodiments, the product data about the AED 10 includes scannedexpiration dates for associated AED pads and battery. In someembodiments, the site-specific parameters include network ID andsecurity credentials. In some embodiments, the location of at least oneof the AED 10 or the AED remote monitoring device 100 is obtained fromGPS coordinates of the mobile device 182. In other embodiments, thelocation of at least one of the AED 10 or the AED remote monitoringdevice 100 is obtained and is pre-programmed into memory either on theserver or the mobile application. Location information may be the formof an street address. Location may also include instructions forlocating a device once the person has entered an address, e.g. “firstfloor, to the right of the main elevator.” In some embodiments, at leastone of the mobile application 310 or the remote management server isfurther configured to check information about a last self-test failureof the AED 10 using the mobile device 182. The information can relate toone or more of: a failure type; a pad expiration details; a batteryexpiration; and a check of log status, for example. In some embodiments,at least one of the mobile application 310 or the remote managementserver is further configured to program the AED 10 with an updatedconfiguration via the mobile device 182. In some embodiments, at leastone of the mobile application 310 or the remote management server isfurther configured to program the AED remote monitoring device 100 viathe mobile device 182. In some embodiments, the communicationsconnection between the mobile device 182 and the AED monitoring device100 is established via a Bluetooth link. In some embodiments, thecommunications connection between the AED monitoring device 100, themobile device 182 and the remote management server is established via aWi-Fi link or a cellular data link 313.

Some embodiments relate to a mobile device application 310 and relatedmethods. For example, a method for AED monitoring utilizing a mobiledevice 182. The method includes establishing, by a mobile application310 configured to be executable on a mobile device 182, a communicationconnection between the mobile device 182 and the AED remote monitoringdevice 100. In embodiments, the method includes establishing, by themobile application 310, a communications connection between the mobiledevice 182 and a remote management server (i.e. centralized monitoringserver 170) that is configured to communicate with the mobileapplication 310 and receive data from the mobile device 182.

In embodiments, the method includes launching, by the remote managementserver, an AED kit engine upon determining that a mobile application 310is activated on the mobile device 182. The method includes executing, bythe remote management server, the AED kit engine to establish an AED kitthat pairs the AED 10 and the AED remote monitoring device 100 andincludes at least product data about the AED 10 and the AED remotemonitoring device 100. The method includes receiving or obtaining, viaat least one of the mobile application 310 or the remote managementserver, an AED kit location. The method includes configuring, via atleast one of the mobile application 310 or the remote management server,the AED monitoring device 100 with site-specific parameters using thecommunications connection. The method includes communicating, via atleast one of the mobile application 310 or the remote management server,a notification of an attempt of the AED monitoring device 100 to connectto the remote management server.

FIGS. 11A-C are screenshots 800A, 800B, and 800C of the interface of amobile application 310 shown on a mobile device 182 for monitoring ofAEDs 10 via remote monitoring devices 100. FIG. 11A shows an example ofa particularly identified AED 10 and a status summary of itemsassociated with the AED 10. Information 802 such as the ID number andmodel number of the AED 10 can be seen, as well as the lot, expiration,and type of the battery and pads. Further, the remote monitoring device100 itself is identified at 804 and can be managed. FIG. 11B shows ascreen with a manage tag option 806 and a remove tag option 808. FIG.11C includes a pop-up request 810 for the remote monitoring device 100to access the devices location. These types of features are useful tothe provisioning process and permit quick and easy pairing of AEDs 10and remote monitoring devices 100.

FIG. 12 is a diagram of the remote monitoring device software subsystem900. The layers of the application include: an application layer 902; anAPI layer 904; a driver layer 906; and a hardware layer 908. Theapplication layer 902 provides the main tasking loop which handles thevarious states and mode of the remote monitoring device 100. The APIlayer 904 abstracts hardware details from the tasking layer 902 byproviding high-level commands and control functions but does not exposeits inner workings or the details of the lower level drivers. The driverlayer 906 directly interfaces to the hardware. The hardware layer 908represents the physical chip or registers in attached peripheraldevices.

In general, embodiments of the software architecture for the remotemonitoring device 100 provide an event driven embedded system, main loopstate machine waiting for events in low power state, and three looselycoupled subsystems. Specifically, the loosely coupled subsystems includeof audio processing, a communications handler, and BLE commandprocessing. Each subsystem processes its own events generated byinterrupts or other subsystems. Functions include running to completion(no pre-emption).

In some embodiments, the remote monitoring device 100 can be understoodto relate to a small battery-powered device that attaches to an AED 10.The remote monitoring device 100 can be connected to the internet viaWi-Fi and report an “I'm OK” signal to the system daily and report anerror message to the system when it detects the AED's chirp whichindicates a failed self-test.

In some embodiments the mobile application 310 can be understood to workwith smart phones (operating on Apple iOS and Google Android OS) andother mobile device 182. The mobile application 310 can connect theremote monitoring device 100 to an AED “kit” on the centralizedmonitoring server 176 and provide a remote interface to both the remotemonitoring device 100 and centralized monitoring server 176.

In various embodiments, IoT/system components provide a subsystem ofcommercial internet components of the overall system, including a remotemonitoring device server 174 (AMS or equivalent that integrates Wi-Fimessages and feeds them to the centralized monitoring server 176), andany other Cloud or user-hosted systems which are required to run theoverall Remote Monitor system. These components are commercial systemswhich use standard internet protocols, and they communicate with eachother and with the centralized monitoring server 176 via ApplicationProtocol Interfaces (APIs).

In some embodiments, the AED 10 can include embedding a signal in theaudible chirp to indicate what issues the AED 10 might have, such aswhether: the electrodes have expired; the electrodes are not functional;or the battery life has expired. These can be heard by the remotemonitoring device 100 but would need to be decoded. This information canbe valuable to the maintenance person but would not impact therapy andwould not provide personal identifiable information. In variousembodiments to address cyber security concerns, AED chirps can beencrypted and not decrypted until they reach a secure server.

In embodiments, remote monitoring device 100 and the related systemand/or its components or systems can include computing devices,microprocessors, modules and other computer or computing devices, whichcan be any programmable device that accepts digital data as input, isconfigured to process the input according to instructions or algorithms,and provides results as outputs. In an embodiment, computing and othersuch devices discussed herein can be, comprise, contain or be coupled toa central processing unit (CPU) configured to carry out the instructionsof a computer program. Computing and other such devices discussed hereinare therefore configured to perform basic arithmetical, logical, andinput/output operations.

Computing and other devices discussed herein can include memory. Memorycan comprise volatile or non-volatile memory as required by the coupledcomputing device or processor to not only provide space to execute theinstructions or algorithms, but to provide the space to store theinstructions themselves. In embodiments, volatile memory can includerandom access memory (RAM), dynamic random access memory (DRAM), orstatic random access memory (SRAM), for example. In embodiments,non-volatile memory can include read-only memory, flash memory,ferroelectric RAM, hard disk, floppy disk, magnetic tape, or opticaldisc storage, for example. The foregoing lists in no way limit the typeof memory that can be used, as these embodiments are given only by wayof example and are not intended to limit the scope of the presentdisclosure.

In embodiments, the system or components thereof can comprise or includevarious modules or engines, each of which is constructed, programmed,configured, or otherwise adapted, to autonomously carry out a functionor set of functions. The term “engine” as used herein is defined as areal-world device, component, or arrangement of components implementedusing hardware, such as by an application-specific integrated circuit(ASIC) or field-programmable gate array (FPGA), for example, or as acombination of hardware and software, such as by a microprocessor systemand a set of program instructions that adapt the engine to implement theparticular functionality, which (while being executed) transform themicroprocessor system into a special-purpose device. An engine can alsobe implemented as a combination of the two, with certain functionsfacilitated by hardware alone, and other functions facilitated by acombination of hardware and software. In certain implementations, atleast a portion, and in some cases, all, of an engine can be executed onthe processor(s) of one or more computing platforms that are made up ofhardware (e.g., one or more processors, data storage devices such asmemory or drive storage, input/output facilities such as networkinterface devices, video devices, keyboard, mouse or touchscreendevices, etc.) that execute an operating system, system programs, andapplication programs, while also implementing the engine usingmultitasking, multithreading, distributed (e.g., cluster, peer-peer,cloud, etc.) processing where appropriate, or other such techniques.Accordingly, each engine can be realized in a variety of physicallyrealizable configurations and should generally not be limited to anyparticular implementation exemplified herein, unless such limitationsare expressly called out. In addition, an engine can itself be composedof more than one sub-engines, each of which can be regarded as an enginein its own right. Moreover, in the embodiments described herein, each ofthe various engines corresponds to a defined autonomous functionality;however, it should be understood that in other contemplated embodiments,each functionality can be distributed to more than one engine. Likewise,in other contemplated embodiments, multiple defined functionalities maybe implemented by a single engine that performs those multiplefunctions, possibly alongside other functions, or distributeddifferently among a set of engines than specifically illustrated in theexamples herein.

Various embodiments of systems, devices, and methods have been describedherein. These embodiments are given only by way of example and are notintended to limit the scope of the present disclosure. It should beappreciated, moreover, that the various features of the embodiments thathave been described may be combined in various ways to produce numerousadditional embodiments. Moreover, while various materials, dimensions,shapes, configurations and locations, etc. have been described for usewith disclosed embodiments, others besides those disclosed may beutilized without exceeding the scope of the present disclosure.

Persons of ordinary skill in the relevant arts will recognize that thesubject matter hereof may comprise fewer features than illustrated inany individual embodiment described above. The embodiments describedherein are not meant to be an exhaustive presentation of the ways inwhich the various features of the subject matter hereof may be combined.Accordingly, the embodiments are not mutually exclusive combinations offeatures; rather, the various embodiments can comprise a combination ofdifferent individual features selected from different individualembodiments, as understood by persons of ordinary skill in the art.Moreover, elements described with respect to one embodiment can beimplemented in other embodiments even when not described in suchembodiments unless otherwise noted.

Although a dependent claim may refer in the claims to a specificcombination with one or more other claims, other embodiments can alsoinclude a combination of the dependent claim with the subject matter ofeach other dependent claim or a combination of one or more features withother dependent or independent claims. Such combinations are proposedherein unless it is stated that a specific combination is not intended.

Any incorporation by reference of documents above is limited such thatno subject matter is incorporated that is contrary to the explicitdisclosure herein. Any incorporation by reference of documents above isfurther limited such that no claims included in the documents areincorporated by reference herein. Any incorporation by reference ofdocuments above is yet further limited such that any definitionsprovided in the documents are not incorporated by reference hereinunless expressly included herein.

For purposes of interpreting the claims, it is expressly intended thatthe provisions of 35 U.S.C. § 112(f) are not to be invoked unless thespecific terms “means for” or “step for” are recited in a claim.

1. A remote monitoring device for monitoring and managing by amonitoring service via a communications network a condition of anautomated external defibrillator (AED) based on audio signals from theAED, comprising: a housing configured to be positioned outside of theAED such that audio sounds from the AED can be detected, the housingcontaining: at least one processor; a communications module operablyconnected to the at least one processor and configured to transmitelectronic communications to the monitoring service via thecommunications network; a first audio sensor; a first audio detectioncircuitry operably connected to the first audio sensor and the at leastone processor, the first audio detection circuitry configured togenerate a wakeup notification signal when the first audio detectioncircuitry detects audio sounds during a predetermined detectioninterval; a second audio sensor; and a second audio detection circuitryoperably connected to the second audio sensor and the at least oneprocessor, the second audio detection circuitry configured to power onin response to the wakeup notification signal and commence an activelistening mode to provide digital audio signals to the at least oneprocessor, wherein the at least one processor is configured to power onin response to the wakeup notification signal, process the digital audiosignals, and transmit a signal to the monitoring service to report acondition of the AED based on the digital audio signals that areprocessed.
 2. (canceled)
 3. The remote monitoring device of claim 1,wherein a power consumption necessary for operation of the first audiodetection circuitry is less than a power consumption necessary foroperation of the second audio detection circuitry. 4-6. (canceled) 7.The remote monitoring device of claim 1, wherein the second audiodetection circuitry is turned on prior to completion of an audio soundfrom the AED initially detected by the first audio sensor or during asubsequent audio sound from the AED.
 8. The remote monitoring device ofclaim 1, wherein the at least one processor is further configured topower down once the signal is transmitted to the monitoring service.9-11. (canceled)
 12. The remote monitoring device of claim 1, furthercomprising an optical sensor operably connected to the at least oneprocessor to detect whether the AED presents a visual indication of anAED self-test failure.
 13. (canceled)
 14. The remote monitoring deviceof claim 1, wherein the signal transmitted to the monitoring serviceidentifies a serial number of the AED.
 15. The remote monitoring deviceof claim 1, wherein an audio sound from the AED includes informationbased an encoding scheme, and wherein the at least one processor isconfigured to analyze the digital audio signals to cause the signaltransmitted to the monitoring service to include status information ofthe AED based on the encoding scheme.
 16. The remote monitoring deviceof claim 15, wherein the encoding scheme is a frequency shift keyingtechnique.
 17. The remote monitoring device of claim 1, wherein thefirst audio detection circuitry is configured to power on during thepredetermined detection interval.
 18. The remote monitoring device ofclaim 15, wherein the audio sound from the AED communicates as part ofthe message at least one of the following: a self-test failure of theAED; a battery expiration; and an electrode expiration. 19-20.(canceled)
 21. The remote monitoring device of claim 1, wherein an audiosound from the AED includes variations in at least one of: an inter-tonetiming, and a length, of the audio sounds that are used to conveyinformation to be decoded by the at least one processor.
 22. The remotemonitoring device of claim 1, wherein the at least one processor isconfigured to power down if any of these conditions are not met: a firstqualifying tone is not detected in the digital audio signals during afirst active listening interval; a second qualifying tone is notdetected in the digital audio signals during a second active listeninginterval; or a third qualifying tone is not detected in the digitalaudio signals during a third active listening interval.
 23. A remotemonitoring device for monitoring audio signals from an automatedexternal defibrillator (AED) and electronically reporting to amonitoring service via a communications network, comprising: a housingconfigured to be positioned outside of the AED such that audio soundsfrom the AED can be detected, the housing containing: a communicationsmodule configured to transmit electronic communications to themonitoring service via the communications network; a first audio sensor;a first audio detection circuitry operably coupled with the first audiosensor, the first audio detection circuitry configured to detect audiosounds from the AED via the first audio sensor; a second audio sensor; asecond audio detection circuitry operably coupled with the second audiosensor, the second audio detection circuitry configured to detect theaudio sounds from the AED via the second audio sensor; and at least oneprocessor operably coupled with the communications module, the firstaudio detection circuitry, and the second audio detection circuitry, theat least one processor configured to: power on the first audio detectioncircuitry during a periodic detection interval to detect the audiosounds during the periodic detection interval, process signals from thefirst audio detection circuitry and generate a wakeup notificationsignal in response to the detected audio sounds during the periodicdetection interval, activate the second audio detection circuitry tocommence an active listening mode in response to the generated wakeupnotification signal, process signals from the second audio detectioncircuitry during the active listening mode to make a determination thatthe AED is in need of service, and transmit a report signal to themonitoring service based on the determination that the AED is in need ofservice.
 24. (canceled)
 25. The remote monitoring device of claim 23,wherein a power consumption necessary for operation of the first audiodetection circuitry is less than a power consumption necessary foroperation of the second audio detection circuitry. 26-28. (canceled) 29.The remote monitoring device of claim 23, wherein the second audiodetection circuitry is activated prior to completion of the audio soundsdetected during the periodic interval or during a subsequent audio soundfrom the AED within the periodic detection interval.
 30. The remotemonitoring device of claim 23, wherein the at least one processor isfurther configured to power down once it transmits the report signal tothe monitoring service. 31-33. (canceled)
 34. The remote monitoringdevice of claim 23, further comprising an optical sensor operablyconnected to the at least one processor to detect whether the AEDpresents a visual indication of an AED self-test failure. 35-36.(canceled)
 37. The remote monitoring device of claim 23, wherein theaudio sounds from the AED include information based an encoding scheme,and wherein the at least one processor is configured to analyze thesignals from the second audio detection circuitry to cause the reportsignal transmitted to the monitoring service to include statusinformation of the AED based on the encoding scheme.
 38. The remotemonitoring device of claim 37, wherein the encoding scheme is afrequency shift keying technique.
 39. The remote monitoring device ofclaim 23, wherein the audio sounds from the AED communicate at least oneof the following: a self-test failure of the AED; a battery expiration;and an electrode expiration. 40-41. (canceled)
 42. The remote monitoringdevice of claim 23, wherein the audio sounds from the AED includevariations in inter-tone timing and length to convey information of theaudio sounds that are used to convey information to be decoded by the atleast one processor.
 43. The remote monitoring device of claim 23,wherein the periodic detection interval is one of a set of configurabledetection intervals that each last 35 seconds or less and can beprogrammed to reoccur after a period of time between 2 minutes and 4hours.
 44. A remote monitoring device for monitoring audio signals froman automated external defibrillator (AED) and electronically reportingto a monitoring service via a communications network, comprising: ahousing configured to be positioned outside of the AED such that audiosignals from the AED can be detected, the housing containing: acommunications module configured to transmit electronic communicationsto the monitoring service via the communications network; at least oneaudio sensor; at least one audio detection circuitry operably coupledwith the at least one audio sensor, the at least one audio detectioncircuitry configured to detect audio sounds from the AED via the atleast one audio sensor; and at least one processor operably coupled withthe communications module and the at least one audio detectioncircuitry, the at least one processor configured to: process signalsfrom the at least one audio detection circuitry based on the detectedaudio sounds, detect a first audio signal from the processed signals, inresponse to the first audio signal being detected, commence an activelistening mode to detect a second audio signal from the processedsignals and confirm that the second audio signal meets a predeterminedcriterion associated with the active listening mode; in response to thesecond audio signal being detected, re-commence the active listeningmode to detect a third audio signal from the processed signals andconfirm that the third audio signal meets the predetermined criterionassociated with the active listening mode, and transmit a report signalto the monitoring service if the third audio signal meets thepredetermined criterion.
 45. The remote monitoring device of claim 44,wherein the predetermined criterion associated with the active listeningmode is different than at least one criteria used by the at least oneaudio detection circuitry to detect audio sounds from the AED.
 46. Theremote monitoring device of claim 44, wherein the predeterminedcriterion associated with the active listening mode are based on atleast one of: a pulse width, a frequency, an amplitude, and a pulseinterval, of each tone in the audio signals.
 47. The remote monitoringdevice of claim 44, wherein the at least one audio sensor mutes for aninterval during the active listening mode between the second audiosignal and the third audio signal. 48-49. (canceled)
 50. The remotemonitoring device of claim 44, wherein the at least one processor isfurther configured to power down once it transmits the report signal tothe monitoring service. 51-54. (canceled)
 55. The remote monitoringdevice of claim 44, wherein the audio sounds from the AED includeinformation based an encoding scheme, and wherein the at least oneprocessor is configured to analyze the processed signals from the atleast one audio detection circuitry to cause the report signaltransmitted to the monitoring service to include status information ofthe AED based on the encoding scheme.
 56. The remote monitoring deviceof claim 44, wherein the audio sounds from the AED communicate at leastone of the following: a self-test failure of the AED; a batteryexpiration; and an electrode expiration.
 57. (canceled)
 58. The remotemonitoring device of claim 44, wherein the audio sounds from the AEDinclude at least one of variations in inter-tone timing and length toconvey information as part of the report signal.
 59. The remotemonitoring device of claim 44, wherein the at least one processor isconfigured to power down if the second audio signal does not meet thepredetermined criterion or if the third audio signal does not meet thepredetermined criterion. 60-109. (canceled)